home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Format CD 36
/
Amiga Format CD36 (1999-01-22)(Future Publishing)(GB)[!][issue 1999-02].iso
/
-seriously_amiga-
/
misc
/
mrcookie
/
mrcookie.readme
< prev
next >
Wrap
Text File
|
1998-11-25
|
4KB
|
140 lines
short: Fully Functional FORTUNE Flinger! (v1.0)
author: lairfight@softhome.net
uploader: lairfight@softhome.net
type: text/misc
MrCookie v1.0 - Never hit a man with glasses; hit him with your fist!
Programmed by Linus Akesson, aka. !LAiRFiGHT! of fLATLiNE
http://fly.to/linus.world
How do I operate this thing?
============================
Well, try it out from Shell. Then you might start experimenting with scripts and
the c:join command, but try it manually first.
TEMPLATE: MrCookie SOURCE/M,MAX=MAXLINES/K/N,MIN=MINLINES/K/N,MW=MAXWIDTH/K/N,
TOP=TOPLINE/S,NOAD/S,CENTER/K/N,PEN=TEXTPEN/K/N,
BPEN=BORDERPEN/K/N,CLS=CLEAR/S,INFO/K,SEL=SELECT/K/N,
HEADER/K,FOOTER/K,PROMPT/K,WIN=WINDOW/S,SCREEN/K,
LEFT=LEFTEDGE/K/N,TOP=TOPEDGE/K/N
Source: This is the file where MrCookie looks for its fortune cookies. It has
the format:
fortune cookie #1
%%
fortune cookie #2
%%
fortune
cookie
#3
%%
etc., the file ends with %% followed by a linefeed. Please have a
look at the included example file.
You may specify any number of files here.
Max: Determines how many lines MrCookie will accept for one cookie. If the
randomly cookie is longer, another one is selected. If that one
doesn't fit, another one is selected and so on. (You can break
MrCookie with Ctrl-C.) Default is no limitation.
Min: Determines how many lines a fortune cookie at least must have.
Mw: Determines how many characters wide a fortune cookie can be. MrCookie
will keep selecting new cookies until one is found that fits the limit.
Top: Flag, this will display a line of "-"s aboce the fortune cookie. This
line will, just as the optional ad at the bottom of the cookie, adapt
its size according to the cookie being displayed.
NoAd: Don't display my little advertisement at the bottom. Now let's quote
the intuition autodocs a bit: Please use this flag thoughtfully and
carefully.
Center: Note that this isn't a flag, it expect a numeric value describing how
many columns wide your display is. In my shell-startup, for example, I
have "CENTER 106" in the MrCookie command line.
Pen: What pen to use when rendering the text. This must be 0-7, since
we're talking ANSI codes.
BPen: Borderpen, the pen used for the Top and Ad lines.
Cls: Insert a clear screen character at the beginning.
Info: Using this attribute you can change the appearance of the top line of
"-"s (if you selected one, please read under "Top".). You can add
your own text here, which will be displayed in the top line and then
padded with "-"s. HOWEVER! The number of the current fortune cookie
is automatically inserted at the end of this string. You should use
the Header option to create your own headers.
A good example of the usage of this attribute is:
INFO "Fortune cookie #"
Sel: Select a certain fortune cookie by number. Perhaps someone has some use
for this...
Header: Type this file before displaying the cookie.
Footer: Type this file after displaying the cookie.
Prompt: Go into interactive mode. After displaying the cookie, the prompt you
specify will be displayed, and if the you press enter a new cookie
will be displayed. You can also enter "q" to quit.
Win: Lame window mode. Not buggy, just lame.
Screen: Public screen to open the window on, if you by chance should be using
the win option.
Left: Set window x position. (Only with Win option.)
Right: Set window y position. (Only with Win option.)
I wanna know moooooooooore!
===========================
This program is freeware. I probably won't update it very much, as it works
well. I've been using it for years now.
The program generates a file called <cookiefile>.map. This file is used to
speed up loading; it contains offsets to all the fortune cookies in the
cookie file. If the size of the cookie file changes, MrCookie will regenerate
the map file. However, if you edit the cookie file and accidentally end up
with exactly the same size as you had before, you'd get some weird output
from the program. If this happens, just delete the .map file.
Please gimme a mail at lairfight@softhome.net!